fix: prevent sorting of measuring points when none are available for water wells#274
Closed
jirhiker wants to merge 1 commit into
Closed
fix: prevent sorting of measuring points when none are available for water wells#274jirhiker wants to merge 1 commit into
jirhiker wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests.
|
Contributor
|
Measuring points are required for each well. Are we transferring some where that's not the case? |
Contributor
|
It's a required field in Which is used to validate the incoming data: https://github.com/DataIntegrationGroup/NMSampleLocations/blob/staging/transfers/well_transfer.py#L343 I'll look to see if the |
Member
Author
|
removed hack from transfer branch to insert wells with no measuring point |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
This PR addresses the following problem / context:
How
Implementation summary - the following was changed / added / removed:
Notes
Any special considerations, workarounds, or follow-up work to note?